Metamodeling Languages and Metaprogrammable Tools

ion over the object models of various underlying back-end persistence technologies. UDM supports multiple such back-ends as shown in 1.3. Figure 1.3: Universal Data Model Framework With the GMeta back-end, the model object network physically resides in GME’s relational internal object database. Direct access to this database is accomplished through the GMeta domain-generic API. With the XML back-end, the model object network resides in an XML file which may be manipulated through the domain-generic DOM API. The generated UDM API for a DSML is a code-level realization of the UML metamodel used to specify the abstract syntax of the DSML. This domain-specific API is a wrapper facade for the domain-generic UML API, which in turn is a wrapper facade for the domain-generic API of each supported underlying model persistence mechanism. Consequently, different metatransformations are used to metaprogram UDM for each of the supported back-ends. For example, the metatransformation for the GMeta back-end may be formalized as: UMLTGMeta : UMLADSML → GMetaADSML (1.4) It is often useful to construct a domain-specific UDM API which supports a DSML originally specified Published in the Handbook of Real-Time and Embedded Systems, Ed. Insup Lee, Joseph Leung, Sang H. Son, CRC Press, 2006